Styles of Scripting.

Hi,
Which is better among the two methods for DXL Scripting
1. Embedding the DXL into an Attribute?
2. Running the DXL in the DXL Window and fetching the data to that particular attribute.

My constraint is when I choose to do that by selecting the Option 1, then it takes more time for loading the objects. If it is a single time execution of the attribute, then it may take more time for the update during the execution time along and not all the times, since the object does not need to reload the data everytime.
Lion29 - Thu Feb 04 07:08:52 EST 2010

Re: Styles of Scripting.
llandale - Thu Feb 04 15:36:46 EST 2010

If the information to be auto-populated in that attribute is completely contained within that one module, then an AttrDXL will work fine. For example, setting the "Need-QA-Check" to true when the "Object Text" changed more recently than the "QA-Check" attribute.

When the info comes from other modules, usually via links, then AttrDXL has the problem that the other modole must be and stay open. Also, attrDXL by nature cannot be very complicated (with included libraries) since not everyone who opens the module will have access to the same network server folders.

The problems with auto-filling on-demand is that you need exclusive access to the module to do that, and if you schedule it for running at night then the info gets stale as the day progresses.

A nice benefit of AttrDXL is that it doesn't execute at all until some obj-attr value is retrieved, either its in a view or some DXL reads it. Thus, infrequently used attributes don't cause any slow down at all.

Usually, I use on-demand scripts running at night primarily because what I do is very complicated.

  • Louie

Re: Styles of Scripting.
Marlx - Thu Feb 04 17:24:16 EST 2010

It is up to the person who wants it......

Re: Styles of Scripting.
Lion29 - Mon Feb 08 07:15:15 EST 2010

Marlx - Thu Feb 04 17:24:16 EST 2010
It is up to the person who wants it......

the only thing that i find is the time required for the auto-populate the data.
When we embed the script into an attribute, and the time required for fetching the data is large, then it will take more time for getting the data.

When we don't embed the script into an attribute, then its only a matter of one time run and one time fetching of the data.

Hence my recommendation is not to make use of the embedding of the scripts... :-)